Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1182

reference: 207-tree-1
name: 1182
tree-preservation-order: undefined
207-tpo-1
uprn
address-text
point: POINT (-1.028471 50.866686)
geometry: MULTIPOLYGON (((-1.028429 50.866682,-1.028431 50.866690,-1.028437 50.866698,-1.028446 50.866704,-1.028458 50.866708,-1.028471 50.866709,-1.028484 50.866708,-1.028496 50.866704,-1.028506 50.866698,-1.028512 50.866691,-1.028514 50.866682,-1.028512 50.866674,-1.028506 50.866667,-1.028497 50.866660,-1.028472 50.866655,-1.028459 50.866656,-1.028447 50.866660,-1.028437 50.866666,-1.028431 50.866673,-1.028429 50.866682)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL